Command Line Version

Top  Previous  Next

The command line version of BurnInTest does not have a Graphical User Interface and as such does not require any graphical libraries to be installed but require ncurses to display information. This also means it is missing some of the tests from the GUI version, the 2D and 3D tests, and has a text based config file so it can be edited in a text editor. The 64 bit version (bit_cmd_linex64) included in the download.

 

Use the number keys to navigate to the different test information pages while the tests are running and use Esc to exit BurnInTest.

 

Notes:

Due to the limited amount of available space on the network test screen the values for the send and received packets are abbreviated to display as K (thousand), M (million) and B (billion).

 

Text Based Configuration File

The text based configuration file (cmdline_config.txt) can be edited in any text editor. The “#” symbol is used to comment out lines and any lines starting with a “#” will be ignored.  Each section of the config file begins with a <SectionName> tag and the valid sections are;

-<Logging>

-<Notes>

-<PreTest>

-<PostTest>

-<DutyCycles>

-<Memory>

-<Disk>

-<CPU>

-<USB>

-<Network>

-<CDRWDVD>

-<Serial>

-<Parallel> (x86 only)

-<Sound>

-<PCIE> (x86 only)

-<Management>

-<Battery>

-<Temperature>

-<Plugin>

-<Errors>

 

For sections that can have multiple tests (eg Disk, Serial) a <Test> tag is used to add a new device and </Test> used to signify the close of that particular section. The default config file is commented with expected values for each section.

 

Logging Section

Flag

Meaning

Valid Keywords / Range

LogFilename

Location (path) of log file

Valid path to place log file

LogPrefix

String to prefix to log name

Text string

Format

Format of log

Ascii, HTML or certificate

LogDetailLevel

Detail level of information logged

summary, normal

TraceLevel

Trace level of information logged

0, 1, 2

MaxFileLines

Max file lines per log

100 - 10000

LogMode

Logging mode, single/multiple files

ClearAppend, AccumulateAppend, ClearNew, Timestamp  

 

Notes Section

Flag

Meaning

Valid Keywords / Range

MachineType

One line description of the machine type

Text string

MachineSerial

Custom serial No. for this machine

Text string

Notes

One line description of extra notes

Text string

 

PreTest Section

Flag

Meaning

Valid Keywords / Range

Action

Action before tests start

None or ExternalWait

ExternalPath

If using ExternalWait this is the path of the file or script to launch and wait for the end of it's execution

Valid path to external script or executable to launch and wait for it to complete

 

PostTest Section

Flag

Meaning

Valid Keywords / Range

AutoStopPassed

Auto stop action when tests have passed

Stop, RunApp or Reboot

ManualStopPassed

Manual stop action when tests have passed

Stop or RunApp

ExternalPathPassed

If using AutoStopPassed RunApp this is the path of the file or script to launch before exiting

Valid path to external script or executable

ExternalParamsPassed

If using AutoStopPassed RunApp this is the parameters to pass to the application being launched

Text string

UseSystemBeepPassed

Emit a system beep on pass


DisplayResultsPassed

Display the results window on pass


AutoStopFailed

Auto stop action when tests have failed

Stop, RunApp or Reboot

ManualStopFailed

Manual stop action when tests have failed

Stop or RunApp

ExternalPathFailed

If using AutoStopFailed RunApp this is the path of the file or script to launch before exiting

Valid path to external script or executable

ExternalParamsFailed

If using AutoStopFailed RunApp this is the parameters to pass to the application being launched

Text string

UseSystemBeepFailed

Emit a system beep on fail


DisplayResultsFailed

Display the results window on fail


 

Duty Cycles Section

Flag

Meaning

Valid Keywords / Range

AutoStopMinutes

Auto stop after specified minutes

0+ (0 for run forever)

AutoStopCycles

Auto stop after specified cycles

0+ (0 for run forever)

CPU

Duty cycle load

1-100

CDDVD

Duty cycle load

1-100

Memory

Duty cycle load

1-100

Serial

Duty cycle load

1-100

Parallel

Duty cycle load

1-100

Disk

Duty cycle load

1-100

Network

Duty cycle load

1-100

USB

Duty cycle load

1-100

Sound

Duty cycle load

1-100

PCIE

Duty cycle load

1-100

 

Memory Section

Flag

Meaning

Valid Keywords / Range

<Test pattern name>

Pattern setting for test

Cycle, Sequence, Binary1, Binary2, Zeros, Ones

 

Disk Section

Each partition being tested and it's related parameters should be enclosed in a <Test>...</Test> section.

For partitioned drives they must be mounted before BurnInTest can test them, they also need to be of partition type ext2, ext3, ext4, reiserfs, xfs,zfs, vfat or ntfs. Due to limited NTFS support in some Linux distributions you may need to use a non-default type (eg ntfs-3g) to mount NTFS drives with read + write permissions before you can test them.

Flag

Meaning

Valid Keywords / Range

Device

The device or partition to be tested

Valid partition eg /dev/sdb2  or raw un-partitioned device /dev/sdc

TestMode

The test pattern

Cyclic, Sequential, HighLow, Binary1, Binary2, Zeros, Ones, Random, RandomSeeking

FileSize

File size as % of disk space

1-15

DutyCycleOverride

Duty cycle override

0 - 100

SeekCount

Seek count

0-10000




 

If the config needs to be setup so all disks are tested these flags can be used, they need to be in the <Disk> Section and don't need to be enclosed in a <Test> section like individual partitions. The individual <Test> sections for specific partitions should not be used when using these flags:

Flag

Meaning

Valid Keywords / Range

TestAllDisks

Select all detected mounted partitions for testing

N/A

TestAllRAWDisks

Select all detected RAW (unpartitioned) disks for testing

N/A

FileSize

File size as % of disk space when using the TestAll options

1-15

TestMode

The test pattern when using the TestAll options

Cyclic, Sequential, HighLow, Binary1, Binary2, Zeros, Ones, Random, RandomSeeking

 

ExcludeDisks

Exclude mount point or device name from "Test all" option

A list of mount points (/) or device names (/dev/sda) seperated with ',' characters

 

CPU Section

Flag

Meaning

Valid Keywords / Range

General

Enable the general operations test

N/A

FPU

Enable the floating point operations test

N/A

SSE

Enable the SSE instructions test

N/A

SSE2

Enable the SSE2 instructions test

N/A

NEON

Enable the Neon instruction test

N/A

Prime

Enable the prime number test

N/A

 

Network Section

Flag

Meaning

Valid Keywords / Range

IP

IP to test, one IP flag for each test, up to 6

Valid IP or 127.0.0.1

BadPacketRatio

Ratio between good and bad packets before an error is logged

0-99,  set to 0 for every bad packet to generate an error.

TimeOut

Timeout in milliseconds

100 - 200000

TestAllNICs

Bind each IP to a different NIC

N/A

 

 

CD-DVD Section

Each CD/DVD device being tested and it's related parameters should be enclosed in a <Test>...</Test> section.

Flag

Meaning

Valid Keywords / Range

Device

Device to test

Valid CD/DVD device

TestMode

Test to run

Music, Data, Passmark, No

Seek

Additional seek (Passmark test mode only)

0-1000

 

Serial Section

Each serial device being tested and it's test mode should be enclosed in a <Test>...</Test> section:

Flag

Meaning

Valid Keywords / Range

Device

Device to test

ttys0 - ttys63 (can also use ttyUSB)

TestMode

Test mode for device

Loopback, Detect

 

These parameters are only set once for the Serial section and apply to all serial tests:

DisableRTS

When specified disables RTS/CTS and DSR/DTR

N/A

SendReceive

Send/Receive timeout value in milliseconds

100-3000

BaudRate

Baud rate to set for test

110, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400, Cycle115 (cycle to 115200), Cycle230 (cycle to 230400)

 

Parallel Section (x86 only)

Flag

Meaning

Valid Keywords / Range

Device

Device to test

valid parallel port lp0, lp1 etc

TestMode

Test mode for device

Loopback, Detect

 

USB Section

Flag

Meaning

Valid Keywords / Range

AutoSelectUSB

Automatically select all USB plugs found on the system for testing

N/A

NumUSB  

Max number of USB devices to test

1-10

RunUSBBenchmark

Run benchmark test at the start of the USB test

N/A

USB3Connection

USB 3 connection speed Auto, SuperSpeed (5GB/s), HighSpeed (480Mb/s), FullSpeed (Mb/s), Cycle (Cycle between speeds)

Auto, SuperSpeed, HighSpeed, FullSpeed, Cycle

 

Sound Section

Flag

Meaning

Valid Keywords / Range

MaxDistortion    

Max level of distortion before an error

1 - 20

SoundDevName

Sound device name used for testing

plughw, default (other sound alias for system, should be left as plughw in most cases)

 

PCIE Section (x86 only)

Flag

Meaning

Valid Keywords / Range

TestAllPCIE    

Automatically select all PCIe slots with PassMark PCIe cards for testing

N/A

NumPCIE

Number of PCIe cards to tests

1-10

 

Management Section

Flag

Meaning

Valid Keywords / Range

Server    

Management console server address

Valid http address for PassMark management console eg
http://localhost/htdocs/mgtconsolemsghandler.php

Username

Username if HTTP authentication is being used on the webserver


Password

Password if HTTP authentication is being used on the webserver


 

Battery Section

Flag

Meaning

Valid Keywords / Range

TestMode    

Run test as main or pre-test

Main, Pretest

Charge

Comparison mode

Current, Full

ThresholdAbs

Absolute threshold when an error is logged. Only one of this and ThresholdPer should be defined

1-100000

ThresholdPer

Percentage threshold for when an error is logged.

1-99

 

Temperature Section

Flag

Meaning

Valid Keywords / Range

AutoSelectSensors    

Auto select which temperature sensors to watch

N/A

SamplePeriod

SamplePeriod

5+

UseCelcius

Use celcius for temperature scale, only one of this or UseFahrenheit should be defined

N/A

UseFahrenheit

Use Fahrenheit for temperature scale

N/A

StopTestOnHighTemp

Stop testing if a sensor records a temperature higher than the threshold

N/A

<Sensors>

If not using AutoSelectSensors can add sensor names to look for here, must match what BurnInTest displays eg "CPU 0 Core 1".

One sensor per line between the "Sensors" tag (up to maxium 64), threshold after a ',', eg CPU 0 Core 1,90

 

Plugin Section

Each plugin being run should be enclosed in a <Test>...</Test> section.

Flag

Meaning

Valid Keywords / Range

Path

File path of plugin to launch

Valid system path to plugin file

PreTest

Run as a pre-test plugin

N/A

 

These parameters are only set once for the plugin section and apply to all plugins:

RunSeparately

Run each plugin separately

N/A

IgnoreTimeout

Ignore no-operations timeout for plugins

N/A

 

Error Section

Flag

Meaning

Valid Keywords / Range

ActionOnError    

Action to take on error

Continue, Beep, Stop

 

Command Line Parameters

-B

BurnInTest will run in a silent mode and not create a ncurses/terminal window.

 

-C [configname]

BurnInTest will load the config file specified.

 

-x

Don’t automatically exit BurnInTest after tests have finished, the default behavior is BurnInTest will exit once the test run has finished.

 

-k

Register your key stored in the key.dat file. This file needs to be created in the same directory as the BurnInTest executable. When using this flag BurnInTest will expect your username/key, from (and including) the "-----START_OF_KEY-----" to (and including) the "------END_OF_KEY------" flags, to be stored in a file called key.dat in the same directory as BurnInTest. You should paste the key as is. It should be 6 separate lines, 1 each for the start and end flags, 1 for the username and 3 for the key. You will need to restart BurnInTest after registration and you can delete the key.dat file you have created. Do not alter the savedkey.dat file, this is a file maintained by BurnInTest and altering this file will corrupt it.

 

-D [duration]

Sets the test duration to the value specified  in minutes

 

-X [duration]
Sets the test duration to the value specified  in cycles

 

-d

Enables debug mode which will create a debug.log file in the same directory as the BurnInTest executable

 

-p [time]

Sets the update interval (time between display updates) in milliseconds, allowable range 500 ( .5 second) to 300,000 (5 minutes).

 

-J

Cycle Disk test patterns between test files (when cyclic set). This option has been added to allow multiple test patterns to be used across very large disks, without waiting for the disk to be completely tested with one pattern before moving on to the next disk test pattern.

 

-K

Keep the disk test data files on disk when an error is logged. Best used in conjunction with the "Stop on Error" option. This setting will also save the random data blocks used if running the "Random Data" and "Random Data and Seeking"disk tests.

 

-v
Print version information and exit

 

-MGT [MachineID]

Set the Configuration->Report information->MachineID value that is used as the main identifier in the Management console. This value will be used even if another MachineID has been saved as the default MachineID. [Machine ID] can be fixed text or a Linux environment variable that has been set.

This ID needs to be a minimum of 8 characters long and can be a maximum of 15 characters. Characters should be alpha numeric and special characters avoided, invalid characters such as "< > & ' " " will be removed from the ID.

 

For example:

bit.exe -MGT MYMACHINEID

bit.exe -MGT $MAC_ADDRESS